Hybrid memory module and system and method of operating the same

ABSTRACT

A memory module comprises a volatile memory subsystem configured to coupled to a memory channel in computer system and capable of serving as main memory for the computer system, a non-volatile memory subsystem providing storage for the computer system, and a module controller coupled to the volatile memory subsystem, the non-volatile memory subsystem, and the C/A bus. The module controller is configured to control intra-module data transfers between the volatile memory subsystem and the non-volatile memory subsystem. The module controller is further configured to monitor C/A signals on the C/A bus and schedule the intra-module data transfers in accordance with the C/A signals so that the intra-module data transfers do not conflict with accesses to the volatile memory subsystem by the memory controller.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/536,588, filed on Nov. 7, 2014, entitled “Hybrid Memory Module AndSystem And Method Of Operating The Same,” which claims priority to U.S.Provisional Patent Application No. 61/901,439, filed Nov. 7, 2013,entitled “Dynamic Random Access to Non-Volatile Memory,” U.S.Provisional Patent Application No. 61/929,942, filed Jan. 21, 2014,entitled “Memory Channel Storage,” U.S. Provisional Patent ApplicationNo. 61/989,941, filed May 7, 2014, entitled “High Density Hybrid MemorySystems,” U.S. Provisional Patent Application No. 62/041,024, filed Aug.22, 2014, entitled “Apparatus and Methods for Transferring StorageContent,” U.S. Provisional Patent Application No. 62/056,469, filed Sep.26, 2014, entitled “Memory Channel Storage,” and U.S. Provisional PatentApplication No. 62/067,411, filed Oct. 22, 2014, entitled “Hybrid MobileMemory for Random Access,” each of which is incorporated herein byreference in its entirety. The present application is related to U.S.Provisional Patent Application No. 61/512,871, filed Jul. 28, 2011,entitled “High Density DIMMs,” and U.S. patent application Ser. No.13/559,476, filed Jul. 26, 2012, entitled “Flash DRAM Hybrid MemoryModule,” each of which is incorporated herein by reference in itsentirety.

FIELD

The disclosure herein is related generally to memory modules, and moreparticularly to hybrid memory modules having both volatile andnon-volatile subsystems, and system and method of operating the same.

BACKGROUND

Computer systems such as network servers, personal computers, PDAs,mobile phones, video games, scientific instrumentation, industrialrobotics, medical electronics, and so on, rely heavily on the capacityand throughput of their system or main memories and the speed ofaccessing them for optimal performance. Currently, dynamic random-accessmemory (DRAM) is commonly used as system memory. DRAM is a type ofrandom-access memory that stores each bit of data in a separatecapacitor in an integrated circuit. The capacitor can be either chargedor discharged so that these two states are taken to represent the twovalues of a bit, conventionally called 0 and 1. Since capacitors leakcharge, the information eventually fades unless the capacitor charge isrefreshed periodically. Because of this refresh requirement, it is adynamic memory as opposed to SRAM and other static memory.

The structural simplicity of DRAM allows DRAM chips to reach very highdensities, because billions of transistor and capacitor pairs can fit ona single memory chip. On the other hand, DRAM is volatile memory—itloses its data quickly when power is removed. Compared to Flash memory,which is a type of electronic non-volatile computer storage medium thatcan be electrically erased and reprogrammed, DRAM is also much moreexpensive. For example, high density DRAM can cost as much as 10 timesmore than high-performance Flash devices. Furthermore, Flash chips canhave much higher density than DRAM chips, allowing a same-sized memorymodule to pack much more to reach a much larger memory capacity.

There are two main types of Flash memory, the NAND type and the NORtype, which are named after the NAND and NOR logic gates. The NOR typeallows a single machine word (byte) to be written or read independently.NAND type Flash memory may be written and read in blocks (or pages),which are generally much smaller than the entire device. NAND Flash alsohas reduced erase and write times, and requires less chip area per cell,thus allowing greater storage density and lower cost per bit than NORFlash. Moreover, NAND Flash also has up to ten times the endurance ofNOR Flash. Thus, NAND Flash has been more widely used than NOR Flash.

Besides its advantages, Flash memory also has certain limitations, whichpose many challenges to make it useful as main memory. One limitation ofFlash memory, especially NAND Flash, is that it can only be erased a“block” at a time. Erasing a block generally sets all bits in the blockto 1. Starting with a freshly erased block, any location within thatblock can be programmed a byte or a word at a time in a random accessfashion. However, once a bit has been set to 0, only by erasing theentire block can it be changed back to 1. In other words, Flash memorydoes not offer arbitrary random-access rewrite or erase operations.

Another limitation is that Flash memory has a finite number ofprogram-erase cycles (typically written as P/E cycles). Mostcommercially available Flash products are guaranteed to withstand arounda certain number of cycles (e.g., 100,000 P/E cycles) before the wearbegins to deteriorate the integrity of the storage. Some chip firmwareor file system drivers perform the so-called wear leveling technique bycounting the writes and dynamically remapping blocks in order to spreadwrite operations between sectors. For portable consumer devices, thesewear-out management techniques typically extend the life of the Flashmemory beyond the life of the device itself, and some data loss may beacceptable in these applications. For high reliability data storage,however, it is not advisable to use Flash memory that would have to gothrough a large number of programming cycles.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a computer or server system according tocertain embodiments.

FIG. 2 is a block diagram of a hybrid memory module having a volatilememory subsystem, a non-volatile memory subsystem and a modulecontroller according to certain embodiments.

FIG. 3 is a block diagram of the volatile memory subsystem in the hybridmemory module according to certain embodiments.

FIG. 4 is a block diagram of the module controller in the hybrid memorymodule according to certain embodiments.

FIG. 5 is a block diagram of a software stack of the computer or serversystem according to certain embodiments.

FIG. 6 is a block diagram illustrating different data paths supported bythe hybrid memory module according to certain embodiments.

FIGS. 7A and 7B are flowcharts illustrating respectively page-in andpage-out processes in the computer/server system according to certainembodiments.

FIG. 8 is a block diagram illustrating interleaving of page-in data flowwith normal memory accesses to avoid data access conflicts according tocertain embodiments.

FIG. 9 is a block diagram illustrating multiple HVDIMMs being usedtogether to provide system memory and/or storage on a memory channel.

FIG. 10 is diagram illustrating a memory association table according tocertain embodiments.

FIG. 11 is a diagram illustrating a memory structure in the computer orserver system according to certain embodiments.

FIG. 12 is a diagram illustrating memory spaces in the hybrid memorymodule during a memory window operation.

FIG. 13 is a block diagram of an exemplary DMA controller according tocertain embodiments.

FIG. 14 is a flowchart illustrating memory window operation processesaccording to certain embodiments.

FIGS. 15A and 15B are flowcharts illustrating respectively processescarried out by the module controller to open and close a memory windowin the hybrid memory module according to certain embodiments.

FIG. 16 is a block diagram illustrating the hybrid memory moduleaccording to further embodiments.

FIGS. 17A and 17B are flowcharts illustrating respectively RAID 3processes for writing data into and reading data from the non-volatilememory subsystem in the hybrid memory module according to certainembodiments.

FIGS. 18-20 are block diagrams illustrating error detection/correctionroutines conducted by the module controller according to certainembodiments.

FIGS. 21-22 illustrate a conventional SSD or Flash operation.

FIGS. 23-26 illustrate Memory Window operations in the hybrid memorymodule according to certain embodiments.

FIG. 27 illustrates a simplified example of a round-robin wear levelingtechnique according to certain embodiments.

FIG. 28 illustrates a hybrid memory module coupled directly to anotherhybrid memory module or any other storage devices via their respectivenetwork interface circuits.

FIG. 29 illustrates one or more hybrid memory modules in a server systemin an intranet network being coupled directly to the intranet networkvia respective network interface circuits.

DESCRIPTION OF THE EMBODIMENTS

As shown in FIG. 1, a computer or server system (computer system) 100according to certain embodiments includes a central processing unit(CPU) or processor, a memory controller (MC), and one or more memorymodules coupled to a system bus. The one or more memory modules providea system memory, and may further provide storage. In certainembodiments, the MC may be integrated into the CPU. In furtherembodiments, the computer system may also include a direct datamanagement controller (DMA) also coupled to the system bus. The CPU withor without the MC and/or the DMA, or the computer system 100 in part orin while, is sometimes referred to hereafter as the “System” or“system.”

In certain embodiments, the computer system 100 may further include anetwork card and one or more I/O devices such as keyboard, monitor,touchscreen, microphone, speaker, etc. The network card may or may notbe integrated into the CPU and provides network interface functions(wired or wireless) between the computer system 100 and local and/orwide area networks. The computer system 100 may further include a PCIbus, which is coupled to the system bus via a north bridge and one ormore storage devices, such as a hard drive, a CD/DVD drive, and a USBdrive, via a south bridge.

FIG. 2 is a block diagram of a Hypervault™ dual-in-line memory module(HVDIMM) 200, which can be used to provide the system memory and/or thestorage of the computer/server system according to certain embodiments.As shown in FIG. 2, the HVDIMM 200 includes a volatile memory subsystem(HV-DRAM) 210, a non-volatile memory subsystem (HV-Flash 220) 220, and amodule control subsystem (HV Controller) 230, mounted on a module board201, which may include one or more printed circuit boards. The HVDIMM200 may also include a data buffer (HV-DB), and may also include anetwork interface controller (HV-NIC). In certain embodiment, the HV-DB240 includes DRAM memory, such as terabyte DRAM memory (TBM). TheHV-DRAM 210 and the HV Controller 230 are coupled to each other, to thesystem, and to the HV-Flash 220 via data signal lines (as represented bythe dashed double-arrow lines) and control/address (C/A) signals lines(as represented by the solid double or single-arrow lines). As shown inFIG. 2, data signal lines 251, 252, and 253, together with the HVController 230 and the HV-DB 240, form a dedicated data path between theHV-DRAM 210 and the HV-Flash 220, allowing data to be transferredbetween the volatile and non-volatile subsystems without going throughthe memory channel or the CPU. In certain embodiment, the dedicated datapath is a high-bandwidth data path.

As is also shown in FIG. 2, the HVDIMM 200 further includes switches,FET-A (e.g., Field-effect transistor or FET switches). In certainembodiments, there are two sets of switches in the HVDIMM 200, dataswitches and command/address switches. These switches do not need to befast switches but they should support relatively short input to outputdelay time. In certain embodiments, the signal propagation time for bothsets of switches should be a small fraction of a data period (e.g.,200-300 ps), so that the delay time can be hidden from the system.

As shown in FIG. 2, data from the system is directly connected toHV-DRAM 210 data input/output (I/O) (not shown) while the systemcommand/address signals are connected to the HV-DRAM 210 via the FETswitches, such that the HV-DRAM 210 either can receive command/addressfrom the system during, for example, normal operations when the systemaccesses the memory spaces in the HVDIMM 200, or from the HV Controller230 during, for example, backup/restore operations when the HVDIMM 200backs up the content in the HV-DRAM after a power failure or restore thecontent back into the DRAM after power is resumed. The FET switches canbe controlled by the HV Controller 230.

In certain embodiments, the HV-Flash 220 includes MLC NAND Flash, whichare partitioned to support fast access as well as enhance the errorcorrection capability for virtual duplication. In certain embodiments,the HV-Flash 220 includes, for example, 256 GB/512 GB of main Flash and32 GB of scratch Flash. The main Flash can serve as a large storage withdirect data bus on the HVDIMM 200 to the DRAM. The scratch Flashfacilitates a mechanism to prolong the life time of the Flash memorycells in the HV-Flash 220, as described below.

FIG. 3 is a block diagram of the HV-DRAM 210 subsystem according tocertain embodiments. As shown in FIG. 3, the HV-DRAM 210 subsystemincludes DERAM devices 310, a registered control device (RCD) or controlregister 320 to interface with the MC or the HV Controller 230, andload-reduction data buffers (LRDB) 330. In certain embodiment, the RCD320 can be a standard register, which is a register in compliance withan industry standard, such as the Joint Electron Device EngineeringCouncil Double Data Rate 4 Load Reduction Dual In-Line Memory Module(JEDEC DDR4 LRDIMM) standard, so that the HV-DRAM 210 can be compatiblewith a standard system memory interface. In certain embodiments, thedata transmission circuits described in commonly owned U.S. Pat. No.8,516,185, which is incorporated herein in its entirety, can be used asthe LRDB 330. Although FIG. 3 shows the LRDB 330 as one unit, inpractice, the LRDB 330 can include multiple units distributed across themodule board 201 and coupled to respective groups of memory devices, asdescribed in U.S. Pat. No. 8,516,185.

In certain embodiments, the HV-DRAM 210 provides main memory functionsfor the HVDIMM 200 when the HVDIMM 200 is used to provide system memory.In certain embodiments, the HV-DRAM 210 acts as buffer memory for theHV-Flash 220 when the HVDIMM 200 is used to provide storage. In certainembodiments, cache-line-wide reads from the DRAM is mapped to the Flash.There are, however, differences between a standard DRAM module (e.g.JEDEC DDR4 LRDIMM) and the HV-DRAM 210. In certain embodiments, theHV-DRAM 210 may include data switches (FET-D), in addition to thecommand/address switches (FET-A). The data switch FET-D is coupledbetween DRAM data buffers (LR-DB) and the DRAM, while thecommand/address switch FET-A is coupled between the memory channel C/Abus and the RCD 320. The FET switches, FET-A and FET-D, can becontrolled by the HV Controller 230 to transition the HVDIMM 200 betweendifferent operation modes. In certain embodiments, either or both ofthese switches, FET-A and FET-D, are not required, and the differentmodes of operation can be accomplished by tristating the relevant I/Osin the DRAM, the HV Controller 230, and/or the LRDB 330.

FIG. 4 is a block diagram of the HV Controller 230, which can include anapplication-specific integrated circuit (ASIC) device or a programmablefield gate array (FPGA) device. As shown in FIG. 4, the HV Controller230 includes control logic 410, a data buffer 420, local memory 430 andregisters 440. The HV Controller 230 further includes a DRAM interface450, a Flash interface 460, a system management Bus interface 470, and anetwork interface 480. In certain embodiments, the HV Controller 230controls data transfers between the HV-DRAM 210 and HV-Flash 220. Itkeeps an address management table in the local memory on-chip memoryspace, operates FET switches, and generates proper commands to theHV-Flash 220 and HV-DRAM 210 for data transfers therebetween.

In certain embodiments, the HV Controller 230 also keeps an HVDIMM 200level bad block table in the local memory and manages the scratch Flash,as discussed below. In certain embodiments, the HV Controller 230 isconfigured to execute error detection/correction routines to insure theintegrity of data stored in the Flash, to perform Flash life extensionoperations by averaging out the HV-Flash 220 block usage and/or usingthe scratch Flash to minimize/reduce program/erase operations in themain Flash.

In certain embodiments, the control logic 410 includes logic circuitsand may further include one or more processing units to pre-process databeing transferred from the Flash to the DRAM, so as to save DRAM memoryspace and reduce data traffic in the memory channel by off-loading someof the computing work traditionally done by the CPU, as discussedfurther below.

In certain embodiments, the HVDIMM 200 can be operated to back up datain the DRAM in response to power failure events. The HV Controller 230provides correct timings for HV-DRAM 210 to be operated in an DLL-offmode when data in the DRAM is being transferred to the Flash. The HVController 230 also provides proper operational procedure for theback-up and restore processes. The FET switches, FET-A, can beconfigured to isolate the RCD 320 and the HV Controller 230 from the C/Abus and to allow the RCD 320 to receive C/A signals from the HVController 230 during the back-up and restore processes.

In certain embodiments, the HVDIMM 200 is configured to allow the systemto access it via a system management (SM) bus using, for example, theI²C protocol or any other system control bus interface. For example, thesystem can also use the SM bus to configure the HV Controller 230 bysetting certain registers in the HV Controller 230. The HV Controller230 can also use the SM bus to notify the system when certain operationis completed or when an error is encountered, either using apreconfigured interrupt signal, or by updating a predefined statusregister in the system bus interface of the HV Controller 230, or in theDMA.

In certain embodiments, the HV Controller 230 also manages networkinterfaces between the HVDIMM 200 and any local or wide-area networks inconjunction with HV-NIC so as to facilitate direct data transfersbetween the HVDIMM 200 and other storage devices in the local orwide-area networks. In certain embodiments, the HV Controller 230includes a network interface and/or is coupled to a network interfacecard (HV-NIC), which can take the data from the HV-DRAM 210 and/orHV-Flash 220, and constructs network packets with proper source anddestination addresses. In general, the source address is pre-configuredby the system. In certain embodiments, the HV-NIC or network interfaceand some or all of the other components of the HV Controller 230 can beembedded into a same ASIC or FPGA.

In addition to the hardware components shown in FIG. 1, the computersystem 100 also includes software/firmware components. In certainembodiments, the software/firmware components can be roughly representedas a stack of software/firmware layers 500 over a hardware layer 501. Asshown in FIG. 5, the stack of software/firmware layers include anapplications layer 510 sitting on an operating system layer 520. Theapplications 510 are software programs that perform specific tasks. Theoperating system 520 manages the hardware and software resources of thecomputer system 100 and acts as an intermediary between the applicationprograms 510 and the hardware components of the computer system 100.

The operating system 520 includes a kernel 521, which are computerprograms that manages input/output requests from other software programs(or processes), and which translates the requests into data processinginstructions for the CPU and/or other hardware components of thecomputer system 100. The kernel can include an interrupt handler thathandles all requests or completed I/O operations that compete for thekernel's services, a scheduler that determines which programs share thekernel's processing time in what order, and a supervisor that actuallygives use of the computer to each process when it is scheduled. Thekernel may also include a manager of the operating system's addressspaces in memory or storage. The kernel's services are requested byother parts of the operating system or by applications through aspecified set of program interfaces sometimes referred to as systemcalls.

Between the kernel and the hardware layer is the basic input/outputsystem (BIOS) layer 530, which in certain embodiments is firmware storedin some sort of permanent memory (e.g., programmable read-only memory(PROM), or electrically programmable read-only memory (EPROM)) andincludes program codes for initializing and testing the system hardwarecomponents, and to load the operating system from a mass memory devicewhen the computer system 100 is boot up. The BIOS may additionallyprovides an abstraction layer for the hardware components so as toprovide a consistent way for application programs and operating systemsto interact with the hardware components such as the system memory andinput/output devices.

In certain embodiments, the software stack further includes an HV driver550 in, for example, the kernel. The HV driver 550 is a software programfor controlling system access to the HVDIMM 200. Thus, the HVDIMM 200can operate like a standard DIMM (e.g., DDR4 LRDIMM) without requiringany changes to the BIOS. The HV driver 550 has access to a memory space560 in the CPU or one or more other memory devices in thecomputer/server system, which is used to store lookup tables or otherconfiguration information, and which the HV driver 550 can consult withand/or update as needed. In certain embodiments, the driver interceptssystem calls to access the HV-Flash 220 and/or HV-DB 240 and directs thememory controller to send control, address and data signals in responseto the system calls and in compliance with the memory interface standardthe system is using (e.g., the JEDEC DDR4 LRDIMM Standard). In certainembodiments, the FET switches, FET-A, are configured to allow both theRCD 320 and the HV Controller 230 to receive the C/A signals from the MCduring normal system operation, and the HV Controller 230 is configuredto monitor the C/A signals from the memory controller and to recognizeand act upon C/A signals formulated in response to system calls toaccess the HV-Flash 220 and/or the HV-DB 240.

For example, as shown in FIG. 6, which illustrates different data pathssupported by the HVDIMM 200. The dash/dotted lines represent the normalsystem read/write data path 610, by which the system performs read/writeoperations with the HV-DRAM 210 via the standard memory interface. Thedotted lines represent a page-out (or swap-out) data path 620, by whichthe HVDIMM 200 transfers data from the HV-DRAM 210 to the HV-DB 240and/or the HV Flash under the control of the HV Controller 230 and inresponse to system request to move the data from the main memory to thestorage so as to, for example, make space in the main memory for data tobe swapped in. The dashed lines 630 represent a page-in (or swap-in)data path, by which the HVDIMM 200 transfers data from the HV-DB 240 orthe HV-Flash 220 to the main memory under the control of the HVController 230 and in response to system request to move the data fromthe storage to the main memory for random access by one or more softwareprograms.

In certain embodiments, normal system access to the main memory isconducted between the system and the HV-DRAM 210, without muchinvolvement from the HV driver 550 or the HV Controller 230. In certainembodiments, the memory interfaces in the computer system 100 aredesigned to be slave interfaces without per command handshake provision.So, the system does not have knowledge about whether any on-DIMM(intra-module) activities are occupying the DRAM I/Os. For example, ifthe DRAM I/Os are being occupied for transferring data between mainmemory and storage, and the system (memory controller) initiates a dataread or write command with the expectation that the DRAMs would be readyto execute the system command, the DRAMs would fail to execute thesystem read/write operation and the system would experience a ‘memoryfailure’, which leads to a system failure.

In certain embodiments, for operations involving the HV-Flash 220 orHV-DB 240, such as a swap-in or swap-out operation, the HV driver 550and the HV Controller 230 work together to move data in or out of themain memory without causing conflict with normal system access to themain memory. In certain embodiments, the HV-driver sends a memory accessrequest to the memory controller when it needs to transfer data betweenDRAM (main memory) and Flash (storage) and provides the DRAM and theFlash addresses with this request. The memory controller may interleavethe HV-driver requests with normal system memory access requests.

In certain embodiments, after receiving a page-in command to transferdata from the HV-Flash 220 to the HV-DRAM 210, the HV-controllermonitors the memory read/write commands from the memory controller. Ifthe memory address for a write command matches the target DRAM addressin the page-in command, the HV-controller replace the write data fromthe system with the data from the Flash. On the other hand, afterreceiving a page-out command to transfer data from the HV-DRAM 210 tothe HV-Flash 220, the HV-controller monitors the memory read/writecommand from the memory controller. If the memory address for a readcommand matches the source DRAM address in the page-out command, theHV-controller snoops the DRAM read data, and transfer the DRAM read datato the Flash.

For example, as shown in FIG. 7A, when a page-in request is issued, theHV Driver would intercept the page-in request and formulate a page-incommand and memory-mapped I/O (MMIO) signal values according to thepage-in request, which may include a source address range in the storageand a destination address in the main memory. The HV driver 550instructs the memory controller to issue the page-in command to theHVDIMM 200. The page-in command uses the same set of C/A signals as astandard write command but with one or more designated C/A signals(e.g., chip select signal(s)) asserted or deasserted to indicate thatthis is not a normal write command for the DERAM devices 310 to respondto. The memory controller would schedule and send the page-in command asif it is a standard write command. The RCD 320 in the HV-DRAM 210 isconfigured to recognize this page-in command and would not forward theC/A signals to the DERAM devices 310. The HV Controller 230 on the otherhand has been monitoring the C/A signals and would act upon the page-incommand by controlling the data transfer between HV-DRAM 210 and theHV-Flash 220 or HV-DB 240.

In certain embodiments, the HV Controller 230 in response to the page-incommand may set the FET switches, FET-D, to direct the data signalsassociated with the page-in command to the HV Controller 230. These datasignals represent the MMIO values formulated by the HV driver 550 andinclude further information/instructions related to the swap-in request,such as what addresses to take data from in the HV-Flash 220 and whataddresses in the HV-DRAM 210 to place the data. In certain embodiments,after receiving the MMIO signals, the HV Controller 230 may checkwhether the requested page-in data has already been loaded into theHV-DB 240, and if not, the HV Controller 230 would initiate and controldata transfer from the HV-Flash 220 to the HV-DB 240 by reading thepage-in data from the HV-Flash 220 and writing the page-in data to theHV-DB 240 using the data buffer 420 in the HV Controller 230 astemporary storage for the page-in data between the read and writeoperations. In certain embodiments, after all page-in data aretransferred to the HV-DB 240, the HV Controller 230 may reload some ofthe page-in data into the data buffer 420 in the HV Controller 230,reset the FET-D switches to allow the HV-DRAM 210 to perform normalmemory operations with the memory controller, and wait for the commandfrom the memory controller to write the data into the HV-DRAM 210.

In certain embodiments, the HV driver 550 is configured to wait for acertain amount of time to allow the page-in data to be transferred fromthe HV-Flash 220 to the HV-DB 240. The HV driver 550 may determine theamount of time based on how much data is being paged-in. Afterwards, theHV driver 550 would instruct the memory controller to schedule and senda dummy write command to the HVDIMM 200. In certain embodiments, thedummy write command is like a normal write command except that it isfollowed with dummy data or no data from the memory controller. The HVController 230 would recognize the dummy write command since it isdirected at the same addresses the page-in data should be placed. Inresponse, the HV Controller 230 would set the FET-D switches and wouldprovide the page-in data to the DERAM devices 310. The dummy data fromthe memory controller is thus ignored or discarded. In certainembodiments, the HV Controller 230 output the page-in data to the DERAMdevices 310 a certain time period after receiving the dummy writecommand so that the data appears at the DRAM I/Os in accordance with theCAS latency parameters of the DERAM devices 310. After page-in dataassociated with the dummy write command has been written into DRAM, theHV Controller 230 would reset the FET-D switches to allow the DRAM toperform normal system memory operations.

In certain embodiments, the HV Controller 230 is configured to monitorthe memory commands from the memory controller and schedule on-DIMM(intra-module) data transfers accordingly to avoid data accessconflicts. In certain embodiments, the HV Controller 230 would workaround system memory accesses when placing the page-in data at the DRAMI/Os, so as to avoid system failure caused by such data accessconflicts. For example, as illustrated in FIG. 8, as data A through Gare being paged in from the HV-DB 240 (TBM) to the main memory (MM), thesystem may also be issuing memory access commands to write data M, M+1,M+2, M+3 into the main memory (MM). The memory controller may schedulethe memory commands from the system and the dummy write commands fromthe HV driver 550 as follows:

CAS TBM A (not shown)—which is a dummy write command from the HV driver550 to transfer data A from TBM to main memory (MM);

CAS TBM B—which is a dummy write command from the HV driver 550 totransfer data B from TBM to main memory (MM);

CAS sys M—which is a normal write command to write data M from systeminto MM;

CAS TBM C—which is a dummy write command from the HV driver 550 totransfer data C from TBM to main memory (MM);

CAS sys M+1—which is a normal write command to write data M+1 fromsystem into MM;

CAS sys M+2—which is a normal write command to write data M+2 fromsystem into MM;

CAS TBM D—which is a dummy write command from the HV driver 550 totransfer data C from TBM to main memory (MM);

CAS TBM E—which is a dummy write command from the HV driver 550 totransfer data C from TBM to main memory (MM);

CAS TBM G—which is a dummy write command from the HV driver 550 totransfer data C from TBM to main memory (MM);

CAS sys M+3—which is a normal write command to write data M+3 fromsystem into MM; and

CAS TBM H (not shown)—which is a dummy write command from the HV driver550 to transfer data H from TBM to main memory (MM).

Before the system issues the CAS TBM B command, the HV Controller 230(referred to in the figure as “FPGA”) may have issued CAS TBM A′, CASTBM B′, and CAS TBM C′ commands to the TBM to output data A, data B, anddata C to the HV CONTROLLER. The HV Controller may preload data A anddata B from the TBM (as shown by the data blocks A and B in the “FPGApg-in input from TBM”) and place it in the data buffer 420 in the HVController. Afterwards, data C is output from the TBM in response to CASTBM C′ from the HV Controller.

The HV Controller continues to issue CAS TBM D′ to the TBM when the HVController observed the CAS sys M command from the system. In response,the HV Controller issues a DES/NOP command to the TBM to pause the datatransfer between the TBM and the MM. Thus, FPGA page-in (Pg-in) outputis paused, as shown by the gap between data B and data C in the FPGAPg-in output, and system data M (Sys) is received by at the MM input.Afterwards, the HV Controller continues to issue CAS TBM E′ to the TBMwhen it observed CAS sys M+1 and later CAS sys M+2 from the system. Inresponse, the HV Controller issues two consecutive DES/NOP commands topause the TBM from outputting data to the HV Controller. As a result, nodata is output between data E and data F from the TBM, and no databetween data C and data D is driven from the HV Controller to the MM,leaving a gap in the HV Controller output to the MM to allow the MM totake system data M+1 and M+2 (Sys).

In certain embodiments, the HV Controller 230 is further configured toperform shadowed data transfer operations between the HV-DRAM 210 andthe HV-Flash 220. For example, when a system command targets a DRAMaddress that has been preprogrammed as an address that requires data tobe transferred from the HV-Flash 220, the HV Controller 230 wouldperform such a transfer to enable proper system access to thispreprogrammed address.

The page-out operations can be performed similarly but in oppositedirection and in a different order, as exemplified in FIG. 7B. Thus, thepage-out/page-in process can be orders of magnitude faster than usingPCIe SSD or conventional memory channel storage because the page-in andpage-out data can be transferred between the main memory and the storageon the HVDIMM 200, without going through the memory channel or the CPU.In addition, system performance is further improved because the datatransfer between HV-Flash 220 and HV-DRAM 210 also frees up the mainmemory channel and the CPU. In certain embodiments, data in the HV-Flash220 is stored in DRAM format, so there is no need to convert the dataformat as data is being moved between the HV-Flash 220 and HV-DRAM 210,which is conventionally performed by the CPU.

In certain embodiments, as shown in FIG. 9, multiple HVDIMMs 200, e.g.,HVDIMM 1, HVDIMM 2, etc., can be used together to provide the systemmemory and/or the storage coupled to the CPU/MC via the system bus,which includes a system control/address bus and a system data bus. Sincethe operating system sees the Flash space of all HVDIMM 200 s as aunified HVDIMM 200 storage, and the system may not know which physicalFlash devices are located on which physical HVDIMM 200. As a result, theHV driver 550 could issue a page-out command with the DRAM address onone HVDIMM 200 and the Flash address on another HVDIMM 200.

To address this issue, the HV driver 550 in certain embodiments builds amemory association table, as shown in FIG. 10. Since the operatingsystem views the storage provided all of the HVDIMM 200 s as one storagedisk (say, the K-disk), the driver can partition the K-disk into aplurality of sub-disks, K1, K2, . . . Kn, each associated with the arespective HVDIMM 200. For example, as shown in FIG. 10, the memoryassociation table has 24 entries per CPU, which in certain embodimentsis the number of DIMM socket per CPU. Each entry correspond to arespective HVDIMM 200 and includes the sub-disk number, the HVDIMM 200ID, the minimum and maximum address bounds for the HV-DRAM 210 on theDIMM, and the minimum and maximum address bounds for the HV-Flash 220 onthe DIMM. Thus, by consulting the memory association table, the HVdriver 550 would try to swap data within the address bounds of theHV-DRAM 210 and the HV-Flash 220 on the same HVDIMM 200.

In general, for cost/performance/power reasons, the memories in acomputer/server system are arranged in layers such that faster andsmaller memories are located within (or close) to a memory cores (e.g.,first layer cache), and density and access time increase as memory isphysically and electronically further away from the core. There arelayers of cache memories in a CPU/MC package, and the memory module(s)that are connected to the MC via a dedicated memory channel in thesystem bus is regarded as the main memory, which provides dynamic randomdata access by the CPU. The storage devices are further away from theCPU and are usually very large memories in the system, such as hard discdevices (HDD), solid-state storage devices (SSD), etc., but they do notprovide dynamic random access capabilities.

The memories in the computer system 100 are somewhat similarlystructured, as shown in FIG. 11 except that the storage provided by theHVDIMM 200 are not far away from the CPU and data from the storage canbe moved into the HV-DRAM 210 for random access without going through asouth bridge, or a PCI bus, or even the memory channel. Furthermore, theHVDIMM 200 provides the HV-DB 240, which can act as a cache memory forthe HV-DRAM 210 by storing data which the HV-DRAM 210 does not havespace to hold and which can be quickly moved into the DRAM when neededin response to a dummy write command from the memory controller.

In certain embodiments, the HVDIMM 200 is configured to provide a verylarge, configurable, expandable, dynamic random access system memory toa computer system. The HVDIMM 200 incorporates novel memory cache layertechniques, i.e., the Memory Window techniques, where the HV-DRAM 210holds contiguous and complete sections of HV-Flash 220 for dynamicaccess by the computer system. Thus, the HV-Flash 220 works as a datavault to the HV-DRAM 210, such that the computer system can open up aMemory Window (MW) in the HV-Flash 220 and bring needed data stored inthe HV-Flash 220 to the HV-DRAM 210 via Memory Window for dynamic randomaccess by the System.

In certain embodiments, the HVDIMM 200 can perform two types ofoperations concurrently: standard memory operation (SMO), as discussedabove, and Memory Window operation (MWO). During SMO, the HVDIMM 200provides a standard main memory space via a standard protocol (e.g., theJEDEC DDR4 LRDIMM protocol). During MWO, as shown in FIG. 12, a specificmemory area (MW), such as a Flash segment or block, in the HV-Flash 220is opened up to support high speed dynamic random access by the computersystem. Requested data in the specific memory area is moved from theFlash to the DRAM. If the system requests to open up more MWs than theDRAM space is allowed, the system has the option to have the HVDIMM 200overwrite the least recently used (LRU) DRAM area, or overwrite aspecific DRAM location. The data from a DRAM area is moved back from theHV-DRAM 210 to the HV-Flash 220 either when there is no more open pagesfor a specific duration (by default), or when the system specificallyrequests to save the data. The MWO can be a background operation that iscontrolled by the HVDIMM 200 controller (HV Controller 230).

Thus, to the computer system, the HV-Flash 220 can also be viewed as avery high-speed access storage because data does not need to be movedfrom a separate storage unit to the main memory, and because data fromany specific memory area in the Flash can be accessible via the memorychannel upon request from the system to open up a MW. In certainembodiments, the system can make a single request to open a MW with acertain size.

In one embodiment, the HVDIMM 200 is a multi-rank (e.g., 2-rank) DIMM,and the HV Controller 230 controls each rank independently, so that thesystem can access one rank while the HV Controller 230 performs an MWO.In general, however, it is preferred that the MWO be executed on bothranks in unison for better memory management. Regardless of whether thesystem executes MWO per rank or on both ranks in unison, the HVController 230 can set its internal (per rank) register bits to indicatecompletion of an MWO. As stated above, the system can also configure theHV Controller 230 to generate an interrupt signal when the MWO iscompleted instead of or in addition to setting the register bits.

In certain embodiments, the HV Controller 230 also controls the boot-upprocess for the HVDIMM 200. There are two types of boot; Fresh boot(booting after a clean shut down) and Reboot (booting after a powerfailure). Unlike the Fresh boot case (where there is no valid data inHVDIMM 200), Reboot requires the HV Controller 230 to populate theHV-DRAM 210 with the same data that was in HV-DRAM 210 at the time ofpower-loss.

The HVDIMM 200 can have two very different operation frequencies, the HVmode frequency and the LRDIMM mode frequency. The HV mode frequency isused to transfer data between HV-DRAM 210 and HV-Flash 220 while theLRDIMM mode frequency is used to transfer data between HVDIMM 200 andthe system. In certain embodiments, the HV-DRAM 210 has two operationalmodes, a standard operation mode and a MW mode. During the standardoperation mode mode, the HV-DRAM 210 fully supports standard memoryoperations (e.g., the JEDEC DDR4 LRDIMM operations) including theinitialization and training protocols. When the HV-DRAM 210 is in the MWmode, the HV-DRAM 210 operates with its DLL turned off since the MW modeof operation frequency (HV mode frequency) is much slower (e.g., anorder of magnitude slower) than the frequency range of the DLL, whichcovers the standard operation mode frequency. The HV Controller 230 usesthe HV mode frequency for MW operations, during which the DRAM and RCD320 is put into the JEDEC DLL-off operational state.

In certain embodiments, commencement of a MWO is initiated by a requestfrom the System. FIG. 5 is a block diagram of certain components in theCPU with an integrated MC according to certain embodiments. As thememory channel between the MC and the HVDIMM 200 may not allowsufficient number of address bits to address the entire memory space inthe HV-Flash 220, the System may keep a look-up table about which areasof the HV-Flash 220 have been copied in the HV-DRAM 210 for randomaccess. As shown in FIG. 7A, when the System needs to access a certainmemory area in the HV-Flash 220, the System would check the lookup tableto determine whether data stored in the memory area has been copied to acertain area in the HV-DRAM 210, i.e., a whether a MW is opened in theHV-Flash 220 to allow the System access to the data. If the answer isyes, the MC would proceed to perform memory operations to access thememory area in the DRAM. If the answer is no, the System would send arequest to open the MW in the HVDIMM 200. The request would includeidentification of the memory area in the HV-Flash 220 to be accessed,such as a starting address of the memory area and a size of the memoryarea, and a destination address in the DRAM, to which data from thememory area is to be transferred. If the System needs more than one MWs,more than one requests can be sent one after another. In certainembodiments, the request is sent directly to the HV Controller 230 inthe HVDIMM 200 via the I²C bus or any other system management/controlbus. In certain other embodiments, the request is sent to and processedby the DMA controller so that the System can continue to perform othermemory operations via the memory channel while the MW is being opened.

In certain embodiment, the DMA controller is used to control certainaspects of the MWO processes. FIG. 13 is a block diagram of an exemplaryDMA controller. In certain embodiments, the (DMA) controller can be usedin conjunction with the CPU/MC to initiate and monitor MWO in the HVDIMM200. Without DMA, the CPU/MC can be occupied for part of or the entireduration of a MWO, and is thus unavailable to perform other tasks. Withthe DMA, the CPU can simply initiate a data transfer request to the DMAand then performs other operations while the transfer is in process.When the data transfer is done, the CPU is notified by an interrupt fromthe DMA controller. Thus, the DMA can offload extensive memoryoperations from the CPU. Many hardware systems use DMA, including diskdrive controllers, graphics cards, network cards and sound cards. DMA isalso used for intra-chip data transfer in multi-core processors.Computers that have DMA channels can transfer data to and from deviceswith much less CPU overhead than computers without DMA channels.Similarly, a processing element inside a multi-core processor cantransfer data to and from its local memory without occupying itsprocessor time, allowing computation and data transfer to proceed inparallel.

In certain embodiments, as shown in FIG. 14, the DMA receives a requestfrom the CPU/MC to open a MW (MW) in the HVDIMM 200. The DMA can bufferthe request and forward the same or reformulated request to the HVController 230 via the I²C bus. The DMA can actively monitor theassociated MWO in the HVDIMM 200 and inform the CPU/MC via an interruptwhen the MW is opened.

Characteristics associated with Flash memories such as limited enduranceand slow writes may require the HVDIMM 200 to obtain support from anoperating system (OS) running on the CPU. The OS may also need theknowledge of the movement of pages between the DRAM and Flash so as toknow when to hide the weak characteristics of the Flash. At boot up, theOS needs to allocate memory pages in the DRAM. After write to a certainpage, the OS may also need to know an estimated time when a next writeto the page can be performed. The OS may also need to set page-tableentries for the DRAM pages and Flash pages. Some or all of these taskscan be offloaded to the DMA, which include status registers, internalmemories and control logic 410 to keep track of these activities.

For example, the DMA can store information regarding how long the HVController 230 may need to transfer a certain amount of data from theHV-Flash 220 to the HV-DRAM 210. Thus, the DMA does not need to wait toreceive a notification from the HV Controller 230 before telling theCPU/MC that the memory window has been opened for dynamic random access.Alternatively or additionally, the DMA can break a request to open aMemory Window into multiple requests each for a smaller chunk of data ofa predetermined size (e.g., 4 KB), as the time required to complete eachof such data transfers is more predictable.

Thus, the HVDIMM 200 allows the system to open up a Memory Window in aHV-Flash 220 block for dynamic operation. The system sends the startingaddress and the data size to HV, and the HV Controller 230 opens up theblock of memory containing the data and transfers the amount ofrequested data into the HV-DRAM 210. In certain embodiments, the minimumtransfer size per HV-Flash 220 block is 32 KB, and the maximum size isthe HV-Flash 220 block size (e.g., 4 MB). Therefore, if the transfersize per HV-Flash 220 block is 32 KB, for 8 GB DRAM, the system can openup to 250K HV-Flash 220 blocks simultaneously.

TABLE 1 # of Address type Description bytes HV-FLASH physical addressfor block 64K blocks 2 System (Virtual Physical) Address per block 2HV-FLASH offset addresses with byte size Total of 16 × 1 byte 16 in 32KB unit for Memory Window per offset address block DRAM address (rowaddress) for the HV- Total of 16 × 2 byte 32 FLASH offset address of 32KB unit address 32 GB scratch Flash address for the HV- Total 16 × 3bytes 48 FLASH offset address of 32 KB unit closed

In certain embodiments, the HV Controller 230 is configured to provideHV-Flash 220 address management and keeps track of physical HV-Flash 220addresses in relation to virtual-physical addresses known to the system.This can be done by creating and updating an address mapping table,which maps the system (virtual-physical) address to the HV-Flash 220physical address for tracking the address of any particular Flash block,and to the offset address of each opened (and copied to HV-DRAM 210)memory location within each block. HV Controller 230 uses the offsetaddresses to correctly place data from HV-DRAM 210 back into properlocations within a particular block of Flash memory. Table 1 listsdescription and sizes for a few address types according to certainembodiments.

FIG. 15A illustrates certain processes carried out by the HV Controller230 to open a memory window in the HV-Flash 220 for dynamic randomaddress by the system according to certain embodiments. In certainembodiments, the HV Controller 230 may notify the DMA or CPU/MC that aMemory Window has been opened after data from the memory window has beensuccessfully transferred to the DRAM. In other embodiments, the HVController 230 may predict the time when the transfer would be completedbased on the request for the Memory Window and historical information,and send the notification to the DMA or CPU/MC before the completion ofthe transfer so that the data transfer will be completed when the CPU/MCreceives the interrupt from the DMA or the notification directly fromthe HV Controller 230 and gets around to start the memory operation withthe memory window.

FIG. 15B illustrates certain processes carried out by the HV Controller230 to close a memory window according to certain embodiments. Thesystem may request to close a HV-Flash 220 area via the I²C interface orsome other system control bus interface. The request may include astarting HV-DRAM 210 address and the size of the Memory Window. Incertain embodiments, if the system needs to close one Memory Window butleaves other Memory Windows within a HV-Flash 220 block open, the HVController 230 would not close (update) the HV-Flash 220 block until allMemory Windows within the block are closed.

In case of a catastrophic system failure due to, for example, powerloss, the HV Controller 230 may also assume the responsibility of movingdata from HV-DRAM 210 to HV-Flash 220 and closes the open blocks. Ifnone of updated HV-DRAM 210 data has been stored into HV-Flash 220, themaximum size of data that HV Controller 230 may need to move can be aslarge as the DRAM size, e.g., 8 GB.

In certain embodiments, to make room for a Memory Window in the HV-DRAM210, certain DRAM pages may need to be moved to Flash. The HV Controller230 would execute one or more pre-erased Flash pages and copy the one ormore DRAM pages into the Flash. The copying can be completed withoutslowing or stalling the CPU. Small copies of the DRAM pages can also bestaged or held in the DRAM or in a cache-buffer/scratch-pad in theHVDIMM 200 for the OS to the control.

In certain embodiments, as shown in FIG. 16, the HV Controller 230includes a built-in processor 1610 and associated hardware (e.g., a dualARM cortex A9 core configuration integrated as a part of an FPGA SOC),and can act as a co-processor to provide on-DIMM (intra-module) datahandling, such as searching, sorting, screening, categorizing,structuring, formatting, etc. Thus, certain tasks traditionallyperformed by the system CPU can be offloaded to the co-processor so thatthe overall system performance can be significantly improved. Examplesof such tasks include, but are not limited to, in-memorycompression/decompression (e.g., source of data in one segment of DRAMand processed data in another segment of DRAM), in-memoryencryption/decryption; security authentication, etc. Since theco-processor has direct access to the DRAM main memory or the Flashstorage without system CPU's involvement, the co-processor can compress,encrypt, and authenticate data in on-DIMM memories without system-wideoverhead.

In certain embodiment, software or firmware packages with ApplicationProgramming Interfaces (API) exposed to the system software are providedto support on-DIMM computing/processing. The software or firmwarepackages are run by the co-processor and may include, for example,software development kits (SDK), such as data compression SDK, dataencryption SDK, data authentication SDK, etc. The firmware packages canbe stored on the HVDIMM 200 or they can be downloaded from the system.The software or firmware packages can be configured to support differentfeatures and the configurations (e.g., license bits, bits indicatingenabled functions) can be stored in a one-time programmable device (OTP)on the HVDIMM 200. For example, the HV Controller 230 can compress ordecompress a certain block or section of data stored in the main memoryor the storage on the HVDIMM 200 using a type of compression algorithmspecified by corresponding configuration bits stored in the OTP.

As a further example, when the CPU is running a search process involvinga large amount of data stored in the on-DIMM storage, the HV Controller230 can pre-screen the data to reduce the data size to be handled by theCPU as the data is being transferred from the on-DIMM storage to themain memory. The HV Controller 230 can also sort the data to reduce thedata categorization and collection time. The HV Controller 230 can alsosearch the data to support fast querying of meta data information. In afurther example, the data from the storage can be presearched so thatonly entries that are considered relevant to the search criteria arerequired to go through ECC and be loaded into main memory.

In further embodiments, the HV Controller 230 uses the HV-NIC (which canbe, for example, an Ethernet interface controller) to provide directdata transfer between a network and on-DIMM memory, and dataextraction/correction using the on-DIMM coprocessor, so that data can beloaded directly from the network, to the storage, the main memory, orboth simultaneously, or vice versa, without going through the systemCPU. Thus, the HVDIMM 200 supports efficient data sharing in a clusterenvironment.

For example, multiple HVDIMM 200 s can be used in a Hardoop processingframework, which is an open-source software framework for storage andlarge scale processing of data sets on clusters of CPUs eachrepresenting a DataNode in a distributed computing environment. EachDataNode can include a number of HVDIMM 200 s, which together cancontain, for example, 192 GB of main memory and 3-6 TB of memory channelstorage. Very fast memory channel storage through put rate (e.g., 39 GBper each 2 CPU server) can be achieved because of parallel data transferbetween the Flash and the DRAM on multiple HVDIMM 200 s. Furthermore,the storage on the HVDIMM 200 can be accessed with very low latency(comparable to the latency for accessing the DRAMs) because the storageis accessed through the memory channel. Since data is moved betweenHV-DRAM 210 and HV-Flash 220 without having to go through a storagechannel or PCI interface, very large blocks of data (e.g., up to 1 GB)can be accessed in read dominated operations.

In certain embodiments, as shown in FIG. 16, the HVDIMM 200 provides ahigh bandwidth dedicated data path 1620 between the main memory and thestorage on the HVDIMM 200 to support on-DIMM data processing, and fast‘page swap’ and ‘demand page’ operations. In further embodiment, theon-DIMM data buffer (HV-DB 240) can be a very large data buffer such asterabit memory (TBM) to serve as temporary storage for the on-DIMMprocessing. In certain embodiments, as shown in FIG. 16. the HVDIMM 200also provides another data path 1630 to allow data transfer between thesystem and the HV-Flash 220 via the HV Controller 230 and the HV-DB 240without going through the HV-DRAM 210.

In further embodiments, As shown in FIG. 16, in certain embodiments, theFlash storage on the HVDIMM 200 includes a number of (e.g., 9) standardembedded multi-media card (eMMC) packages each having an embeddedmulti-media interface, a Flash controller and Flash memory. The HVController 230 also includes built-in redundant array of independentdisks (e.g., RAID 3) circuit 1640 that provides dynamic hardware-basederror-correction, full data recovery and data reconstruction, resultingin increased Flash life time. The RAID 3 feature also minimizedrequirement for data duplication.

The eMMCs generally support error correction in hardware. Issues canarise, however, when one of the eMMCs cannot correct certain errors indata from the Flash memory in its package during a read operation. Incertain server systems, storage networks are built with redundancies(e.g., RAID) to enable further correction of errors at the storagesystem level. Before eMMCs were used to form the Flash storage, suchredundancies were helpful as the Flash storage would output uncorrecteddata with error indication. An eMMC, however, does not produce outputdata if it cannot correct the errors in the data. Thus, the missing bitfrom an eMMC can cause system failure and/or unrecoverable data error.

To address this problem, the HVDIMM 200 according to certain embodimentsincludes at least one parity eMMC 1650 (e.g., the 9th eMMC in FIG. 2)that is used to store parity bits associated with the data stored in therest of the eMMCs (“data eMMCs,” e.g., the 1st to the 8th eMMCs in FIG.2). The HVDIMM 200 further includes an error correction (e.g., RAID 3)circuit in, for example, the HV Controller 230. In certain embodiments,the RAID 3 circuit is included in the data paths between the storage andthe system, which may also includes the TBM and/or the main memory, asshown in FIG. 2.

In certain embodiment, as shown in FIG. 17A, when write data is to bewritten to the storage, the RAID 3 circuit receives each set (e.g., 8bytes) of write data from, for example, the TBM, and generates a paritybyte for each set of data bytes. The RAID 3 circuit then outputs thedata bytes together with its associated parity byte for storing inrespective eMMC circuits. During a read operation, as shown in FIG. 17B,the HV Controller 230 outputs control and address signals to instructthe eMMCs to output read data. The RAID 3 circuit would receive sets ofdata bytes from the data eMMCs and parity bytes from the parity eMMC.For each set of data bytes received in parallel, the RAID 3 circuitwould determine if the set of data bytes is missing a byte from one ofthe data eMMCs. If no data byte is missing, the RAID 3 circuit wouldmove the set of data bytes along its intended path. If a data byte ismissing from one of the data eMMCs, the RAID 3 circuit would reconstructthe missing data byte from the set of data bytes and the parity bytereceived in parallel with the set of data bytes and generate areconstructed set of data bytes, which are placed in the TBM forforwarding to the main memory or the system, or stored in a buffermemory in the HV Controller 230 for further processing by the on-DIMMprocessor.

The HV-DB 240 is used to temporarily store data so as to make datatransfers in the HV-DB 240 faster and more efficient. Since normallydata may be transferred in and out of Flash memory at a slower speedthan data is transferred to and from the system, the HV-DB 240 is usedto buffer data to/from the Flash memory so the system does not have toslow down and wait for data to be written to or read from the storagesubsystem. When the system writes data to the storage subsystem, thedata is buffered into the HV-DB 240 at DRAM data I/O speed, which ismuch faster than Flash data I/O speed. The buffered data is written intothe Flash memory on, for example, first in, first out basis. The same istrue for the read direction. Thus, while reading from the storagesubsystem, the CPU can engage in other processes with the main memoryuntil the HV-DB 240 buffer has buffered a predetermined amount of datafor transferring to the main memory or the system at the DRAM speed. Onthe other hand, when data is transferred from the main memory to thestorage, the data is read from the DRAM according to a set ofcontrol/address (C/A) signals from the system or the HV Controller 230and written into the HV-DB 240 according to another set of C/A signalsfrom the HV Controller 230. While the DRAM can be engaged with thesystem on other tasks, the HV Controller 230 can transfer the data fromthe HV-DB 240 to the storage by reading the data from the HV-DB 240 andwriting the data to the storage.

The components in the HVDIMM 200, e.g., the HV Controller 230, the mainmemory subsystem (or volatile memory subsystem), the HV-DB 240, thestorage subsystem (or non-volatile memory subsystem), can be mounted ona same printed circuit board or disposed in close proximity to eachother to allow fast and smooth data transfer therebetween.

NAND Flash can be prone to low-reliability issues due to random errorsgenerated by physical effects in the geometry of the NAND gates. Thus,in certain embodiments, to improve data integrity, the HV Controller 230is configured to carry out a set of error detection/correction routinesto detect and correct errors in the data stored in the HV-Flash 220. Forexample, every time when data is transferred from the HV-DRAM 210 to theHV-Flash 220, the HV Controller 230 would perform error correctioncoding on the data. In certain embodiments, as shown in FIG. 18, thedata bits are grouped and each group of data bits are arranged in athree-dimensional matrix. Cyclic Redundance Check (CRC) codes can becomputed using predetermine algorithm along each of the X, Y and Z axisfor the three dimensions of the matrix. The CRC codes are then storedtogether with the data into the HV-Flash 220. In certain embodiments,the HV Controller 230 includes on-chip memory spaces (e.g., 1 k-2 k ofSRAM) and/or shift registers to store a copy of the data for the CRCcalculation while the data is being transferred from the DRAM to theFlash.

When the data is transferred from HV-Flash 220 to HV-DRAM 210, the HVController 230 would have each group of data arranged again into thesame matrix format, and CRC codes are computed again using the samepredetermined algorithm along each of the axis as shown in FIG. 8. Thenewly computed CRC codes are compared with the corresponding CRC codesreceived with the data. If there were no error in the data, the newlycomputed CRC codes would match the corresponding CRC codes received withthe data. If the received data contain one or more errors as shown inFIGS. 19 and 20, there would be mismatch between the newly computed CRCcodes and the received CRC codes. With the data arranged in the matrixformat, such mismatch in the CRC codes can be used to identify thelocation of an erroneous data bit, and correction can be made by simplyflipping the erroneous data bit at the identified location.

FIG. 19 illustrates an exemplary situation where one of the bits in aX-Y plane of the data matrix (e.g., bit D210) is erroneous. This can bedetected with CRC check in just the X and Y directions to pinpoint thebit location with the error. As shown in FIG. 19, bit D210 is part of arow of bits D010, D110, D210, . . . and D710 along the X direction, andalso part of a column of bits D200, D210, D220, . . . , D290 along the Ydirection. So, if both the newly calculated CRC code for the row of bits(CRC810, CRC910, and CRCA10) and the newly calculated CRC code for thecolumn of bits (CRC2A0, CRC2B0, and CRC2C0) do not match thecorresponding CRC codes received with the data, while all other newlycalculated CRC codes in the same X-Y plane match the corresponding CRCcodes received with the data, the location of the error would be at theintersection of the row of bits and the column of bits, i.e., D210, asshown in FIG. 19.

FIG. 20 illustrates an exemplary situation where two of the data bits ina same X-Y plane in the data matrix (e.g., bit D210 and bit D600) areerroneous. To properly pinpoint the locations of the bit errors, CRCcheck needs to be conducted in X, Y and Z directions. As shown in FIG.10, CRC check conducted in just the X and Y directions in this situationwould indicate four possible locations of bit error (e.g., D200, D210,D600 and D610). Additional CRC check in the Z direction is thus use topinpoint the exact locations of bit error (e.g., D210 and D600).

In certain embodiments, the HV Controller 230 performs CRC checks oncopies of the data which are being transferred from the HV-Flash 220 tothe HV-DRAM 210. Therefore, by the time HV Controller 230 detects a biterror, the erroneous data bit may have already been written into theDRAM. To correct the bit error, the HV Controller 230 can perform aread-modify-write operation to read a segment of data containing theerroneous bit from the DRAM, modify the erroneous bit, and then writethe data segment back into the DRAM.

As stated above, Flash memory has a finite number of program-erasecycles, and frequent erase/write operations can cause Flash memory cellsto wear out, causing reliability issues. To prolong the life of HV-Flash220, the HVDIMM 200 includes a scratch Flash in additional to the mainFlash (as shown in FIG. 12) and the HV Controller 230 is configured toexecute an error detection/correction process when data is moved backand forth between the HV-DRAM 210 and HV-Flash 220. By using the errordetection/correction process, which is discussed below, the HVDIMM 200can support random updates to Flash without reducing the Flash life byavoiding program/erase (P/E) operations to the main Flash as much aspossible.

In certain embodiments, the scratch Flash is employed to hold updated(modified) data when a Flash block is filled. The modified data in thescratch Flash can be incorporated into the Flash block when the systemis ready to close the block. For example, if a particulartask/application requires 100 updates to each of 100 Flash pages inFlash block, 10,000 updates would be needed. If there is 25 initiallyunfilled page areas in a block, this task/application requires 400 P/Eoperations, which amounts to 3.2 GB of data being rewritten. However, ifthe modified data is stored in the scratch Flash, then the block onlyneeds 1 P/E operation. As for the scratch Flash area, only 10,000 pageswill be written, which amounts to only 80 MB of data being rewritten.

In certain embodiments, the scratch Flash, unlike storage or main Flash,does not have to follow the block concept, although it follows standardFlash operations. Thus, each page update is written into the next open(unwritten) page space. A written page is marked as ‘stale’ when eitherthe page is updated again and the updated page is written into a newlocation, or the page is copied into the storage Flash by the systemclosing a block in the storage Flash. When all pages in a physical blockin the scratch Flash are marked as ‘stale’, the block is erased and thenmarked as open (or available). In certain embodiments, for a block thatcontains mostly ‘stale’ pages, the pages that are not marked ‘stale’ arecopied into a new location so that the block can be erased.

FIGS. 21-22 illustrate a conventional SSD or Flash operation where,according to industry standard replacement algorithm, when a systemrequests to open a segment in a Flash block (Block K), the system mustselect a block (Block N) in the main memory (DRAM) to be replaced by theFlash block. A new block in the Flash is opened to accommodate the datain Block N before Block N is replaced by the data in Block K. Anotherblock in the Flash where block N was originally taken from is thereaftererased.

FIGS. 23-24 illustrate a Memory Window operation in the HVDIMM 200according to certain embodiments. Here, in response to a system requestto open a new segment in the main Flash, and a block is selected in theHV-DRAM 210, but only the pages in the DRAM block that are required forthe selected segment (e.g., X pages for segment Y) are actually subjectto replacement. The X pages are written to the scratch Flash before datafrom segment Y is written into the space held by the X pages in theDRAM. Thus, data is moved between HV-DRAM 210 and HV-Flash 220 page bypage and no new blocks in the Non-volatile memory are required to bewritten or erased when the new segment is opened for dynamic randomaccess.

At some point, a current scratch Flash block may be filled up as data ismoved from the Flash to the DRAM page by page. For example, as shown inFIG. 25, if a memory window operation requires M+1 pages to be replacedin DRAM and the current scratch block j only has M pages left unfilled,the first M pages of the M+1 pages can be written into Block j, whilethe M+1^(st) page is written into Block j+1 in the scratch Flash.

The HV Controller 230 is configured to keep track of data movementsamong the main Flash, the DRAM and the scratch Flash. When the systemrequests to close a block in the DRAM, a new block in the Flash isopened to accommodate the data in the to-be-closed block in DRAM. Sincesome of the data in the to-be-close block may have been put in thescratch Flash, the HV Controller 230 is further configured to merge datain the to-be-closed block from the DRAM with the data taken from theto-be-closed block and stored in the scratch Flash, as illustrated inFIG. 26. The merged data is stored in the new block in the Flash and anold block in the Flash where the to-be-erased block in the DRAM wastaken from is thus erased.

In addition to using the scratch Flash to prolong the life of the mainFlash, the HV Controller 230 is also configured to perform wear levelingby equalizing average usage time of each block in the HV-Flash 220. Incertain embodiments, such wear leveling can be done by a round robinmethod. The HV Controller 230 uses its address mapping managementcapabilities and relatively large memory space to keep track of theassociated address changes.

FIG. 27 illustrates a simplified example of a HVDIMM 200 round-robinwear leveling technique, according to certain embodiments. As shown inFIG. 27, both Event Progress Cases 1 and 2 have Blocks 0 and 2 openedfor Memory Window operations. In Event Progress Case 1, File A is closedfirst while in Event Progress Case 2, File C is closed first. Thus, forCase 1, File A is written into the first empty (erased) block (B #3).For Case 2, File C is written into block B #3.

Instead of or in addition to being used as main memory, the HVDIMM 200can also be used as a storage device to facilitate direct data transferswithin an intranet network.

Recent developments in cloud networking and computing require efficientways to transfer and store data. Since the cloud environment supportsmany different types of applications that share computational power aswell as database, any particular server or storage bottleneck can impactthe overall performance of the cloud network.

There are two types of data transfers, intranet and internet. Anintranet provides a closed network within an organization, which sharescomputing resources and information, while internet networks are betweenintranets or between organizations.

Internet (between organizations) data transfers are generally lessconcerned about data transfer latency. On the other hand, intranet datatransfers require prompt responses and is less tolerant of data transferlatency. This is especially true when a task is farmed out to multipleservers for parallel computation using shared operating system, program,and database. In such cases, data coherency is required among theseservers for correctly executing the task. Therefore, any data transferlatency in one server can slow down the task execution.

There are also two types of data transfers in an intranet: datatransfers within each individual server and data transfers amongstvarious servers. The data transfers amongst various servers use internetprotocol technology to share information, operational systems, orcomputing resources. The data transfers within a server is generallyhandled by the CPU, and occur amongst memory devices and networkconnections via the CPU.

Currently, transferring data between intranet servers requires atransmitting server CPU to gather the data from either a storage or fromthe main memory, packetize the data, and put it onto the network. Thereceiving server CPU needs to extract the data and to store it in astorage or the main memory. Transferring data within a server requiresthe CPU to read data from one memory coupled to the CPU and write thedata into another memory device also coupled to the CPU.

For example, when a process running on the CPU attempts to allocate morememory than the system has available, the OS would swap memory pages toand from the storage. If a page is selected for replacement and “PageOut” is referenced again, it has to be paged in (read in from storage).This would involve waiting for I/O completion and the total respondingtime is the sum of:

(Page Out Time)+(Page In Time)

where

(Page Out Time)=(Memory Time)+(CPU Time)+(Bus Time)+(Storage Time)

and

(Page In Time)=(Storage Time)+(Bus Time)+(CPU Time)+(Memory Time).

In both cases, data transfer latency can be reduced if the data does notneed to go through the CPU. In other words, if direct data transferoccurs from a memory device to the network, then the data transferlatency amongst servers will be minimized. Data transfer latency withina server can also be reduced if the data is transferred directly betweenmemory devices without going through the CPU.

In the intranet network, if a process running on the CPU attempts toallocate more memory than the system has available, the OS would swapmemory pages to and from the IO Storage. If the page is selected forreplacement and “Page Out” is referenced again, it has to be paged in.This would involve waiting for I/O completion, but the total respondingtime is now the sum of:

(Page Out Time)+(Page In Time)

where

(Page Out Time)=(Memory Time)+(HV Time)+(Storage Time)

and

(Page In Time)=(Storage Time)+(HV Time)+(Memory Time)

Thus, the total responding time is significantly shortened.

In certain embodiments, the HV Controller 230 is configured tofacilitate data transfers between different HVDIMMs 200 by providing anetwork interface (“Share™ Direct DIMM Interface”) via the HV-NIC. Forexample, as shown in FIG. 28, an HVDIMM 200 (on the left) can be coupleddirectly to another HVDIMM 200 (on the right) or any other storagedevices via their respective NIC devices, and the HV Controller 230 ineither HVDIMM 200 is configured to transfer data between the DRAM on oneHVDIMM 200 and the Flash in the other HVDIMM 200, between the DRAM onone HVDIMM 200 and the DRAM on the other HVDIMM 200, between the Flashon one DIMM and the Flash on the other DIMM, and also between the HVDIMM200 and any other storage devices, using similar techniques as discussedabove.

Additionally, the HV Controller 230 is also configured to facilitatedata transfers between different server systems. For example, as shownin FIG. 29, the HVDIMM(s) 200 in each server system in an intranetnetwork can be coupled directly to the intranet network via theirrespective HV-NIC devices and/or another Network Interface device. Thus,the HV Controller 230 on each HVDIMM 200 in a particular server caninitiate and control data transfers directly between HVDIMM 200 s indifferent servers.

We claim:
 1. A memory module for use in a computer system, the computer system including a memory controller coupled to the memory module via a system bus, the system bus including a data bus and a control/address (C/A) bus, comprising: a volatile memory subsystem coupled to the system bus and capable of serving as main memory for the computer system, the volatile memory subsystem including dynamic random access memory (DRAM) devices; a non-volatile memory subsystem configured to provide data storage for the computer system; and a module controller coupled to the volatile memory subsystem, the non-volatile memory subsystem, and the system bus, wherein the module controller is configured to read first data from the non-volatile memory subsystem in response to a first command received via the memory channel, the first command being a command to transfer data from the non-volatile memory subsystem to the volatile memory subsystem, wherein the module controller is further configured to provide at least one portion of the first data to the volatile memory subsystem a certain time period after receiving a dummy write memory command via the C/A bus so that the at least one portion of the first data appear at inputs/outputs (I/O) of the DRAM devices in accordance with a latency parameter of the DRAM devices, wherein the volatile memory subsystem is configured to receive the at least a portion of the first data in response to the dummy write memory command. 